Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add transaction_id to SEP-12 requests #134

Merged
merged 2 commits into from
Jun 12, 2024

Conversation

philipliu
Copy link
Contributor

@philipliu philipliu commented Jun 12, 2024

This is to support the latest version of the SEP-12 protocol. Tests have not been added because the test anchor does not support the transaction_id fields.

@Ifropc Ifropc merged commit 6c2f855 into stellar:main Jun 12, 2024
1 of 2 checks passed
): AddCustomerResponse {
val customer: MutableMap<String, String> = mutableMapOf()

populateMap(type, customer, memo, sep9Info)

val urlBuilder = URLBuilder(baseUrl)
urlBuilder.appendPathSegments("customer")
urlBuilder.addParameter("transaction_id", transactionId)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@philipliu @Ifropc shouldn't the transaction_id value go in the request body (aka populateMap) instead of a url parameter for this PUT request?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching this. I'll publish a PR to fix this.

@@ -116,6 +127,7 @@ internal constructor(

val urlBuilder = URLBuilder(baseUrl)
urlBuilder.appendPathSegments("customer")
urlBuilder.addParameter("transaction_id", transactionId)
Copy link

@CassioMG CassioMG Aug 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@philipliu @Ifropc same question here: shouldn't the transaction_id value go in the request body (aka populateMap) instead of a url parameter for this PUT request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants